---
title: Controller - Xiaomi WXCJKG11LM Aqara Opple 2 button remote
description: Controller automation for executing any kind of action triggered by the provided Xiaomi WXCJKG11LM Aqara Opple 2 button remote. Supports Zigbee2MQTT, ZHA, deCONZ.
model: WXCJKG11LM
manufacturer: Xiaomi
integrations: [Zigbee2MQTT, ZHA, deCONZ]
model_name: Xiaomi WXCJKG11LM Aqara Opple 2 button remote
---

import {
  Input,
  Inputs,
  Requirement,
  ImportCard,
  Changelog,
} from '/src/components/blueprints_docs'

<ImportCard id='xiaomi_wxcjkg11lm' category='controllers' />

<br />

:::tip
This blueprint is part of the **Controllers-Hooks Ecosystem**. You can read more about this topic [here](/docs/controllers-hooks-ecosystem).
:::

## Description

This blueprint provides universal support for running any custom action when a button is pressed on the provided Xiaomi WXCJKG11LM Aqara Opple 2 button remote. Supports controllers integrated with Zigbee2MQTT, ZHA, deCONZ. Just specify the integration used to connect the remote to Home Assistant when setting up the automation, and the blueprint will take care of all the rest.

In addition of being able to provide custom actions for every kind of button press supported by the remote, the blueprint allows to loop the long press actions while the corresponding button is being held. Once released, the loop stops. This is useful when holding down a button should result in a continuous action (such as lowering the volume of a media player, or controlling a light brightness).

:::tip
Automations created with this blueprint can be connected with one or more [Hooks](/docs/blueprints/hooks) supported by this controller.
Hooks allow to easily create controller-based automations for interacting with media players, lights, covers and more. See the list of [Hooks available for this controller](/docs/blueprints/controllers/xiaomi_wxcjkg11lm#available-hooks) for additional details.
:::

## Requirements

<Requirement id='zigbee2mqtt'/>
<Requirement id='zha'/>
<Requirement id='deconz'/>
<Requirement name='Input Text Integration' required>

This integration provides the entity which must be provided to the blueprint in the **Helper - Last Controller Event** input. Learn more about this helper by reading the dedicated section in the [Additional Notes](#helper---last-controller-event).

[Input Text Integration Docs](https://www.home-assistant.io/integrations/input_text/)

</Requirement>

## Inputs

<Inputs category='controllers' id='xiaomi_wxcjkg11lm' />

## Available Hooks

### Light

This Hook blueprint allows to build a controller-based automation to control a light. Supports brightness and color control both for white temperature and rgb lights.

#### Default Mapping

- Button 1 short press -> Turn on
- Button 1 long press -> Brightness up (continuous, until release)
- Button 1 double press -> Color up
- Button 2 short press -> Turn off
- Button 2 long press -> Brightness down (continuous, until release)
- Button 2 double press -> Color down

[Light Hook docs](/docs/blueprints/hooks/light)

### Media Player

This Hook blueprint allows to build a controller-based automation to control a media player. Supports volume setting, play/pause and track selection.

#### Default Mapping

- Button 1 short press -> Volume up
- Button 1 long press -> Volume up (continuous, until release)
- Button 1 double press -> Next track
- Button 2 short press -> Volume down
- Button 2 long press -> Volume down
- Button 2 double press -> Play/Pause

[Media Player Hook docs](/docs/blueprints/hooks/media_player)

### Cover

This Hook blueprint allows to build a controller-based automation to control a cover. Supports opening, closing and tilting the cover.

#### Default Mapping

- Button 1 short press -> Open cover
- Button 1 long press -> Open the cover tilt
- Button 2 short press -> Close cover
- Button 2 long press -> Close the cover tilt
- Button 2 double press -> Stop cover and cover tilt

[Cover Hook docs](/docs/blueprints/hooks/cover)

## Additional Notes

### Helper - Last Controller Event

The `helper_last_controller_event` (Helper - Last Controller Event) input serves as a permanent storage area for the automation. The stored info is used to implement the blueprint's core functionality. To learn more about the helper, how it's used and why it's required, you can read the dedicated section in the [Controllers-Hooks Ecosystem documentation](/docs/controllers-hooks-ecosystem#helper---last-controller-event-input).

## Changelog

<Changelog category='controllers' id='xiaomi_wxcjkg11lm' />
